home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19990725-20000114
/
000267_news@columbia.edu _Mon Nov 8 12:00:20 1999.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id MAA25065
for <kermit.misc@watsun.cc.columbia.edu>; Mon, 8 Nov 1999 12:00:19 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id LAA14254
for kermit.misc@watsun.cc.columbia.edu; Mon, 8 Nov 1999 11:53:16 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: stevenhill@aol.com (StevenHill)
Subject: SCO Unix 5.05 - setuid and setgrp errors
Date: 08 Nov 1999 16:35:31 GMT
Organization: AOL http://www.aol.com
Message-ID: <19991108113531.00892.00002399@ng-fu1.aol.com>
To: kermit.misc@columbia.edu
We have a situation where we are getting setuid and setgrp errors when C-Kermit
is called from our program. C-Kermit is supplied by a vendor of ours, and we
use it to transmit data to them. If we log in as root, or set it up so that
when a user logs in they go to a prompt rather than running our applicaion, and
then execute kermit from the command line, all works fine. We have about
seventy other clients, all running SCO Unix 5.05, that are not having any
problem at all. The one unique thing about this location is that their file
system is set up such that the directory that our application is run out of is
a virtual link to a partition. That is, our clients are usually set up so that
the application is run from /usr/medical on the root file system, this client
is set up so that the root file system is small, and the have a /dev/medical
file system that is mounted as /usr/medical (or some such thing). Their
hardware people say that /usr/medical is a virtual directory linked to the
/dev/medical file system.
The application is written in C (the version of C that came with SCO Xenix
several years ago, never upgraded and a recent attempt to upgrade to the latest
version of C on SCO Unix resulted in thousands of errors, mostly due to missing
parameters to functions that have changed from then to now)
Any thoughts as to what we can do would be appreciated. If other info is
needed, I will do my best to acquire it.
If you can, please respond to StevenHill@aol.com
Thanks in advance
Steven Hill
Buford, GA USA